Release 10.1A: OpenEdge Deployment:
WebClient Applications

Single sign-on

Progress® Software Corporation recommends that each server the application accesses be protected with a user ID and password. To simplify access to servers, multiple servers might be protected by the same user ID and password. To facilitate single sign-on for the end user, which eliminates the need for the end user to enter the same user ID and password multiple times, WebClient caches authentication information, such as user IDs and passwords, that the end user enters, and gives the application access to this cache.

If the end user so chooses, WebClient maintains the authentication cache across end user sessions. This is called persistent caching. Persistent caching can be disabled by the application deployer, and the persistent cache can be cleared by the end user.

For more information, see the "Implementing single sign-on" section.